Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cameraview: remove glflush #22949

Merged
merged 2 commits into from
Nov 17, 2021
Merged

Conversation

deanlee
Copy link
Contributor

@deanlee deanlee commented Nov 17, 2021

No description provided.

@pd0wm
Copy link
Contributor

pd0wm commented Nov 17, 2021

You can revert 7a3754d if the cpu usage is back to 20%

@pd0wm
Copy link
Contributor

pd0wm commented Nov 17, 2021

Do you still want to look into the blocking of glMap, or is this the best we can do?

@deanlee
Copy link
Contributor Author

deanlee commented Nov 17, 2021

glmap usually blocking for a few milliseconds, and occasionally more than 10ms, it's ok because it's run in vipc thread, the main thread will not be blocked.
I can't think of other ways for the time being to improve the performance of async pbo.

@pd0wm
Copy link
Contributor

pd0wm commented Nov 17, 2021

Oh, assumed it was much more than a few ms. Then this is fine.

@pd0wm pd0wm merged commit 33b1b94 into commaai:master Nov 17, 2021
@deanlee deanlee deleted the cameraview_remove_flush branch November 17, 2021 14:40
@pd0wm
Copy link
Contributor

pd0wm commented Nov 17, 2021

Weird, I really though CPU usage was lower when I tested this change before. Guess I didn't rebuild properly or something. There must be something else we can do to lower CPU.

pd0wm added a commit that referenced this pull request Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants